feat: Adding option --use-kubeconfig in vcluster cli arguments, #1729
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: Adding option --use-kubeconfig in vcluster cli arguments, which specify the kubeconfig file to be used for vcluster cli
What issue type does this pull request address? (keep at least one, remove the others)
/kind feature
What does this pull request do? Which issues does it resolve? (use
resolves #<issue_number>
if possible)resolves #1724
Please provide a short message that should be published in the vcluster release notes
according to the describtion of this issue , I try to work on this and add some code to impliment this feature
well, there is a slightly different thing which is that I use
--use-kubeconfig
as the globalflag, because--kube-config
flag has already been defined in other subcommand, for example when executeWhat else do we need to know?
this
--use-kubeconfig
flag support user inputrelative file path and absolute path